home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_1
/
dirmgr02.zip
/
DIRMGR.DOC
< prev
next >
Wrap
Text File
|
1991-11-05
|
11KB
|
279 lines
DIRMGR
PCBoard Files Listing Directory Manager
Supports:
over 2,100,000,000 files
over 9,200,000,000,000,000,000 bytes
Customized color settings
VERY FAST!
Version 1ß02, 05-November-1991
DIRMGR02.ZIP
For use with PCBoard Versions 14.5x
Copyright (C) 1991 Geoffrey Sy;
ALL RIGHTS RESERVED
See DIRMGR.NEW for a listing of changes since version 1ß01.
This program is supported by:
Geoffrey Sy
51 Wyatt Walk
Toronto, Ontario Canada
M5A 3T3
*
TABLE OF CONTENTS
=================
Introduction ........................................................
Installation ........................................................
Editing DIRMGR's Configuration Files ...........................
Program Capabilities ................................................
Multi-Tasking/Node Support .....................................
Network, File Sharing Support ..................................
Error Codes .........................................................
Bug Report Procedure ...........................................
Support/Registrations................................................
Disclaimers/Copyrights ..............................................
INTRODUCTION
============
This program makes the little ANSI header on PCBoard DIRxx files listings.
I wrote the program because I couldn't find one that is NICE enough or can
handle enough MILLIONS of TERABYTES or or FAST enough.
PROGRAM INSTALLATION/OPERATION
==============================
Step #1:
=======
Make a directory and put the DIRMGR.EXE into it. You can put the DIRCLR.EXE
too if you want. The DIRCLR.EXE was included for removing the headers. This
is needed to prevent some programs that process the DIRxx files from hangups
if there are such headers present.
Step #2:
========
Edit the configuration. I'll include a utility to manage them for you later.
There is a sample file called DIRMGR.CNF that'll give you the idea. This is
a straight ASCII file containing 6 lines, they are as follows:
1 - Header for your DIR file
2 - Header for your DIRxx files
* Both of the above may be substituted with the %D:\PATH\FILE to tell PCB *
* to include such files from disk. Future update will include individual *
* header file for each DIRxx files - well, will see how the support goes. *
3 - Complete pathname to the DIR file. This is the menu that shows up when
the users us the (F)iles command in PCBoard.
4 - Complete pathname to the DIR.LST file. This is the file that contains
all your paths to your DIRxx files and the descriptions for them.
5 - Complete pathname to the New Uploads DIRxx file. This is the file
containing the files description of new conference uploads.
6 - Your customized title for the New Uploads DIRxx area.
Step #3:
========
BACKUP YOUR HARD DRIVE! ...Well at least the DIRxx files. I won't be held
responsible for what happens in the next step.
Step #4:
========
TRIAL RUN.
At the DOS prompt type:
DIRMGR DIRMGR.CNF C:\PCB /INIT
│ │ └── This parameter is needed the first time.
│ └───────── The path to your PCBFILER.DEF file.
└─────────────────── The configuration file created in step #2.
The first time you run DIRMGR, be sure to use the /INIT option. This option
is needed to initialize the directories. The initialization process removes
any old header and adds the macro to display the new header file. After this
process you'll see files with the .$DM extension. These are backups of your
original directories, you may delete them if you don't need them.
While the program is running, full verbose error messages and current status
are displayed on line 6 of the status screen. There's a timer on line 4 and
files/bytes status indicator on line 7.
If you have a runtime error please check the runtime error codes in this
document. If the program just hangs, you're probably running the AT version
on your PC/XT. Make sure you run the correct version as your CPU.
Step #5:
========
Please support ShareWare. If you're going to use the program regularly,
please make a point to register it. Your registration will encourage
further support and development of this and other programs. Without support
and feedback, programs such as this will simply disappear.
PROGRAM CAPABILITIES
====================
+ Will run under a 128K window in DesqView, but will not share or
give up CPU cycles. DirMgr does very fast DMA writes to video
RAM, so screen bleed-through may occur on 286 CPUs running DV.
+ File-sharing has been provided. This doesn't mean that you can
run it unattended while users are on-line, but you can probably
get away with it if the users aren't reading the DIRS description
or the header of the DIRxx files. Make sure SHARE.EXE is loaded.
+ Headers and DIRS description colour settings co-ordinate with
those set in PCBFILER.DEF.
+ Will count OFF-LINE files. DELETED files are not counted. If you
had deleted the file what's the use of including them?
+ Can probably processed at least 2000 lines per second. I haven't
really run any benchmarks on this, but it really feels faster than
all the other programs I've tried. I've included a timer to show
the number of elapsed seconds for you to compare the results with
other similiar programs.
ERROR CODES
===========
Error Class Description
2 DOS: File not found (Check command line)
3 DOS: Path not found
4 DOS: Too many open files (Check CONFIG.SYS)
5 DOS: File access denied
6 DOS: Bad file handle
12 DOS: Bad file access code
16 DOS: Can't remove current dir
15 DOS: Bad drive number
100 I/O: Disk read error
101 I/O: Disk write error
102 I/O: File not assigned
103 I/O: File not open
104 I/O: File not open for input
105 I/O: File not open for output
106 I/O: Bad numeric format (Check numbers in .CNF)
150 CRITICAL: Disk is write-protected
151 CRITICAL: Unknown unit
152 CRITICAL: Drive not ready
153 CRITICAL: Unknown command
154 CRITICAL: CRC error in data
156 CRITICAL: Disk seek error
157 CRITICAL: Unknown media type
158 CRITICAL: Sector not found
159 CRITICAL: Printer out of paper
160 CRITICAL: Device write fault
161 CRITICAL: Device read fault
162 CRITICAL: Network or Hardware failure
200 FATAL: Division by zero
201 FATAL: Range check
202 FATAL: Stack overflow
203 FATAL: Heap overflow
204 FATAL: Bad pointer operation
205 FATAL: Floating point overflow
206 FATAL: Floating point underflow
207 FATAL: Bad floating point operation
208 FATAL: Overlay Manager not initialized
BUG REPORTS
===========
Catch the bug, put it into a ZIPloc bag and upload it to my support board.
Please provide the version number you're using and any message the program
returns as well as the steps required to re-create the error. The current
number is (416) 287-9002 (HST) and (416) 286-8734 (slow). I have no control
over whether or not the board is up. This'll depend on how deep in debt Jeff
(the SysOp of my support BBS) is. If he's in debt he'll need to auction off
his equipments.
SUPPORT
=======
If you have any questions, bugs, or suggestions, please contact me. I may be
reached on the NaNET(tm), ShareWare, Intelec(tm), City2City(tm), Rime(tm),
and other PCBoard echoes. Or by mail to the above address. Registered
users may contact me using the voice number in the registration document.
Since this is user supported software, I don't expect you to register if you
don't like it or if it doesn't meet your needs. Just stop using it after a
reasonable trial period (2-3 weeks). The program is not crippled in any way,
there are no delays, timebombs, etc, etc. If you like the program and use
it regularly, please register it. Registration only costs C$10.00 and you'll
receive unlimited voice support and upgrades. Please mail your registration
to the above address.
Registration entitiles you to unlimited upgrades and support. You may even
call me up at odd hours and your queries don't have to be related to this
package. I can pretty well provide solutions to most of the common PCBoard
operation problems.
STANDARD DISCLAIMERS/COPYRIGHTS
===============================
This program is provided on an "AS IS" basis. No warranty of any kind is
expressed or implied. YOU USE THIS PROGRAM AT YOUR OWN RISK. I take no
responsibility for any damage caused directly or indirectly from the use or
the inability to use this program.
PCBoard - Copyrighted: Clarke Development Company
City2City - Trade Marks of FUTURETRON Online Services
NaNET - Trade Marks of Canada Remote Systems Online Services
Intelec, RIME - Trade Marks of their respeced trademark holders
Other - Copyrighted: Respected Owners